Hi, I have the task of importing 60 word docs into doors modules. I have used the standard way of the in-built addin in word and imported all data to 60 different modules. But this works well only the first time, if there are now updates to the word docs and i need to update the relevant module, then how can this be done? I tried the same, but it only adds to the existing, rather than comparing and updating? Is there any dxl or any tool or any hints anywhere in the forum, which can help me achieve the same?I have searched the forum for many threads, but none gave the solution. But since these were old, hoping this is solved somehow now. Or any guidance is appreciated. I am using doors 9.6.1.9 client Gsquare - Tue Dec 11 07:54:59 EST 2018 |
Re: Word import to doors client:Update of existing module Short answer: you cannot do that Long answer: a.) if you have in your Word document a table format requirements with your own ID and you have also imported that ID to DOORS in the first import, then you can save the Word content as CSV file from Word and use the Spreadsheet Import in DOORS to update the imported requirements b.) you can import the Word docs to new modules and then use module comparison wizard to do a compare on the new and old modules allowing it to create links, thus you can see what has been updated between the versions and (manually) update those which have been changed c.) you can export the old modules to Word and do compares in Word (60 of those?) and based on that information do manual updates My general rule is to say that there is only one import from Word - after that the users have to use DOORS to modify the requirements, not anymore the Word documents |
Re: Word import to doors client:Update of existing module Maybe there is something in existence, but I'm not aware of it. The problem is when you copy data from Word to DOORS the data doesn't always come across great and requires rework in DOORS. So if you had a tool that updates a module, you would likely be required rework it every time you did an import. At that point a Beyond Compare of the documents then pasting the changes manually would probably take the same amount of work and be less risky.
Just and FYI re-creating that tool that imports the data from Word into DOORS isn't a huge task. Once you have that created it would be easy to modify the script to update the module instead of creating new objects. But you still run into the issue of rework, so I'm not sure it is worth it. |
Re: Word import to doors client:Update of existing module PekkaMakinen - Tue Dec 11 08:33:59 EST 2018 Short answer: you cannot do that Long answer: a.) if you have in your Word document a table format requirements with your own ID and you have also imported that ID to DOORS in the first import, then you can save the Word content as CSV file from Word and use the Spreadsheet Import in DOORS to update the imported requirements b.) you can import the Word docs to new modules and then use module comparison wizard to do a compare on the new and old modules allowing it to create links, thus you can see what has been updated between the versions and (manually) update those which have been changed c.) you can export the old modules to Word and do compares in Word (60 of those?) and based on that information do manual updates My general rule is to say that there is only one import from Word - after that the users have to use DOORS to modify the requirements, not anymore the Word documents Thanks for the hint. We actually need to do a ReqIF export from DNG and then import it to doors client. But the problem here is that ReqIF export from DNG when imported into doors client does not import images and tables. Hence we adopted the painful process of word export(doc/rtf) from DNG and then import to doors client. IF the ReqIF export package from DNG and import to doors would work all of this would not have been necessary. |
Re: Word import to doors client:Update of existing module davidcs - Tue Dec 11 08:49:31 EST 2018 Maybe there is something in existence, but I'm not aware of it. The problem is when you copy data from Word to DOORS the data doesn't always come across great and requires rework in DOORS. So if you had a tool that updates a module, you would likely be required rework it every time you did an import. At that point a Beyond Compare of the documents then pasting the changes manually would probably take the same amount of work and be less risky.
Just and FYI re-creating that tool that imports the data from Word into DOORS isn't a huge task. Once you have that created it would be easy to modify the script to update the module instead of creating new objects. But you still run into the issue of rework, so I'm not sure it is worth it. Yes, beyond Compare could be one approach, but again as you said this involves some manual work, especially images and tables. |
Re: Word import to doors client:Update of existing module Gsquare - Tue Dec 11 22:59:36 EST 2018 Yes, beyond Compare could be one approach, but again as you said this involves some manual work, especially images and tables. I do not want to advertise here, but at Continental we have been using the product Reqman from em: AG which does the job very nicely. We use it in our own IT service to transform Word -> ReqIF to be able to get it to DOORS or other systems. Regards, Mathias |
Re: Word import to doors client:Update of existing module Mathias Mamsch - Wed Dec 12 05:34:30 EST 2018 I do not want to advertise here, but at Continental we have been using the product Reqman from em: AG which does the job very nicely. We use it in our own IT service to transform Word -> ReqIF to be able to get it to DOORS or other systems. Regards, Mathias Ok, that's a helpful info. i will try this tool |
Re: Word import to doors client:Update of existing module Gsquare - Tue Dec 11 22:58:17 EST 2018 Thanks for the hint. We actually need to do a ReqIF export from DNG and then import it to doors client. But the problem here is that ReqIF export from DNG when imported into doors client does not import images and tables. Hence we adopted the painful process of word export(doc/rtf) from DNG and then import to doors client. IF the ReqIF export package from DNG and import to doors would work all of this would not have been necessary. Did you try any other of the commercially available ReqIF export tools? I know there are some, like the PTC Requirements Synchronizer, and other companies also did ReqIF exports for DNG ... In addition there is a new version of DNG that has some major improvements with ReqIF Im-/Export ... Maybe you should check it out too. Regards, Mathias |
Re: Word import to doors client:Update of existing module Mathias Mamsch - Fri Dec 14 02:42:44 EST 2018 Did you try any other of the commercially available ReqIF export tools? I know there are some, like the PTC Requirements Synchronizer, and other companies also did ReqIF exports for DNG ... In addition there is a new version of DNG that has some major improvements with ReqIF Im-/Export ... Maybe you should check it out too. Regards, Mathias hello Mathias, No i have not tried any other reqIF export tool, other than the in-built tool available in DNG. Currently we are evaluating the ReqMan tool as suggested by you. It would be great if you could name a few good commercially available ReqIF tools for us to use, which also exports the Images and tables for us to import back to Doors client from DNG without any loss of data. Also, currently we are using DNG v6.0.6, if that helps. |